Management of user interface elements in a display environment

ABSTRACT

A widget manager facilitates management of widgets in a dashboard layer. Management functions can include enablement, preview, importation, exportation, organization, installation, deletion, acquisition, etc.

RELATED APPLICATIONS

This application claims the benefit of priority from U.S. Provisional Patent Application No. 60/737,899, entitled “Management of User Interface Elements In A Display Environment,” filed Nov. 18, 2005, which provisional application is incorporated by reference herein in its entirety.

This application is generally related to the following jointly owned and co-pending patent applications, each incorporated herein by reference in its entirety:

-   -   U.S. Provisional Patent Application No. 60/583,125, for         “Procedurally Expressing Graphic Objects for Web Pages,” filed         Jun. 25, 2004;     -   U.S. patent application Ser. No. 10/874,829, for “User Interface         for Assisting in the Installation of an Asset,” filed Jun. 22,         2004;     -   U.S. patent application Ser. No. 11/145,561, for “Presenting         Clips of Content,” filed Jun. 3, 2005;     -   U.S. patent application Ser. No. 11/145,560, for “Web View         Applications,” filed Jun. 3, 2005;     -   U.S. patent application Ser. No. 11/145,023, for “Clip View         Applications,” filed Jun. 3, 2005;     -   U.S. patent application Ser. No. 11/148,010, for “Preview and         Installation of User Interface Elements in a Display         Environment,” filed Jun. 7, 2005;     -   U.S. Provisional Patent Application No. 60/734,016, entitled         “Preview including Theme Based Installation of User Interface         Elements in a Display Environment,” filed Nov. 4, 2005, which         provisional application is incorporated herein by reference in         its entirety;     -   U.S. Provisional Patent Application No. 60/730,956, entitled         “Widget Security,” filed Oct. 27, 2005, which provisional         application is incorporated herein by reference in its entirety;     -   U.S. patent application Ser. No. 11/282,110, entitled “Preview         including Theme Based Installation of User Interface Elements in         a Display Environment,” filed Nov. 16, 2005; and     -   U.S. patent application Ser. No. 11/346,603, entitled “Multiple         Dashboards,” filed Feb. 1, 2006.

TECHNICAL FIELD

The disclosed implementations relate generally to graphical user interfaces.

BACKGROUND

A hallmark of modern graphical user interfaces is that they allow a large number of graphical objects or items to be displayed on a display screen at the same time. Leading personal computer operating systems, such as Apple Mac OS®, provide user interfaces in which a number of windows can be displayed, overlapped, resized, moved, configured, and reformatted according to the needs of the user or application. Taskbars, menus, virtual buttons and other user interface elements provide mechanisms for accessing and activating windows even when they are hidden behind other windows.

Although users appreciate interfaces that can present information on a screen via multiple windows, the result can be overwhelming. For example, users may find it difficult to navigate to a particular user interface element or to locate a desired element among a large number of onscreen elements. The problem is further compounded when user interfaces allow users to position elements in a desired arrangement, including overlapping, minimizing, maximizing, and the like. Although such flexibility may be useful to the user, it can result in a cluttered display screen. Having too many elements displayed on the screen can lead to “information overload,” thus inhibiting the user to efficiently use the computer equipment.

Many of the deficiencies of conventional user interfaces can be reduced using “widgets.” Generally, widgets are user interface elements that include information and one or more tools (e.g., applications) that let the user perform common tasks and provide fast access to information. Widgets can perform a variety of tasks, including without limitation, communicating with a remote server to provide information to the user (e.g., weather report), providing commonly needed functionality (e.g., a calculator), or acting as an information repository (e.g., a notebook). Widgets can be displayed in a display environment and accessed through a user interface, such as a “dashboard.” Widgets and dashboards are described in co-pending U.S. patent application Ser. No. 10/877,968, entitled “Unified Interest Layer For User Interface.”

Due to the large number of widgets available to a user, a virtual desktop or dashboard can become cluttered and disorganized, making it difficult for the user to quickly locate and access a widget. Moreover, many widgets may not perform as expected or advertised when installed. Some widgets may even present a security risk to the host machine and network resources because they include a virus or are designed to carry out malicious activities. Accordingly, tools are required to manage all aspects of widget deployment and display.

SUMMARY

In some implementations, a user-activated dashboard (also referred to as a “unified interest layer”) is provided that can contain any number of user interface elements, referred to herein as “widgets,” for quick access by a user. In response to a command from a user, the dashboard is invoked and the widgets are shown on the screen. In one aspect, a widget manager is provided as either a stand alone application, part of an installer process, part of the operating system or otherwise to facilitate management of widgets available to the user. Management functions can include enablement, preview, importation, exportation, organization, installation, deletion, acquisition and the like. Other management functions are possible.

Widgets can be of any type. They can communicate with a remote server to provide information to the user (e.g., a weather report), or they can provide commonly needed functionality (e.g., a calculator), or they can act as an information repository (e.g., a notepad or calendar). Some widgets can provide a combination of these types of functions.

Aspects of the invention can include one or more of the following features. The user interface element can be a widget. The display environment can be a dashboard, a desktop, or other display space.

In some implementations, a widget manager includes a management engine operable to present available widgets in a palette of a user interface display environment, to selectively enable or disable each of the available widgets, and to display enabled widgets in the display environment.

In some implementations, a method of managing widgets for display in a display environment includes: presenting a list of available widgets; receiving user input to enable one or more widgets to be displayed in a display environment; indicating in the list which widgets are enabled and to be displayed in the display environment from the available widgets; and at run time, instantiating each enabled widget in the display environment.

In some implementations, a method of managing widgets for display in a display environment includes: determining usage information for widgets when displayed in a display environment; determining usage criteria associated with the presentation of widgets in the display environment; selectively enabling and disabling at least one widget from the available widgets based on the usage criteria and the usage information; and displaying enabled widgets in the display environment.

In some implementations, a method of managing widgets includes: presenting a list of available widgets in a user interface; enabling a subset of the available widgets; and displaying the subset in a display environment of the user interface.

In some implementations, a method of managing widgets includes: determining user privileges; presenting a list of available widgets based on the user privileges; enabling a subset of the available widgets based on user selection; and displaying enabled widgets in a display environment.

In some implementations, a method for managing widgets includes: determining widgets that are available for display; classifying the available widgets; presenting the available widgets according to the classification; selectively enabling ones of the available widgets; and at run time, displaying enabled widgets in a display environment.

In some implementations, a method of managing widgets includes: identifying available widgets for display in a display environment; presenting the available widgets in a management environment; selectively enabling ones of the available widgets; and displaying enabled widgets in the display environment.

In some implementations, a method for managing widgets includes: identifying available widgets for display in a display environment; determining a criteria for selecting ones of the available widgets; and displaying the selected ones of the available widgets.

Other methods, apparatuses, computer-readable mediums and devices having various features are also disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a hardware architecture for previewing, installing, managing and operating widgets in a display environment.

FIG. 2 is a flow diagram of a process for activating and using a dashboard.

FIG. 3 is a block diagram depicting a software architecture for previewing, installing, managing and operating widgets in a display environment.

FIG. 4 a is a screen shot depicting a desktop user interface prior to activation of a dashboard.

FIG. 4 b is a screen shot depicting an initial state for a dashboard.

FIG. 4 c is a screen shot depicting a configuration bar for a dashboard.

FIG. 4 d is a screen shot depicting user selection of a widget from the configuration bar.

FIG. 4 e is a screen shot depicting an installation confirmation.

FIG. 4 f is a screen shot depicting a preview of a user interface element that has been selected to be installed.

FIGS. 4 g-4 i illustrate the deletion of widgets from a configuration bar.

FIG. 5 is a block diagram of an installer process.

FIG. 6 is a flow diagram of a process for installing a user interface element in a display environment.

FIG. 7 a illustrates a user interface for a widget manager.

FIG. 7 b illustrates a widget manager confirmation panel associated with deletion of a widget.

FIG. 7 c is a block diagram of a widget manager process.

FIG. 7 d illustrates a user interface for invoking a widget manager.

FIG. 7 e illustrates an alternative user interface for invoking a widget manager.

FIG. 7 f illustrates a user interface for a widget management window.

FIG. 7 g illustrates a user interface for use in sorting widgets.

FIG. 7 h illustrates an alternative user interface for a widget management window.

FIG. 7 i illustrates a user interface for deleting widgets.

FIG. 7 j shows a method for managing widgets.

FIG. 7 k shows an alternative method for managing widgets.

FIG. 8 a shows an alternative method for managing widgets.

FIG. 8 b shows a method for managing a subset of widgets.

FIG. 8 c shows a method for managing widgets including privilege processing.

FIG. 8 d shows a method for displaying widgets based on classification.

FIG. 8 e shows an alternative method for managing widgets.

DETAILED DESCRIPTION Hardware Architecture

FIG. 1 is a block diagram of a hardware architecture 100 for previewing, installing, managing and operating widgets in a dashboard. The architecture 100 includes a personal computer 102 coupled to a remote server 107 via a network interface 116 and a network 108 (e.g., local area network, wireless network, Internet, intranet, etc.). The computer 102 generally includes a processor 103, memory 105, one or more input devices 114 (e.g., keyboard, mouse, etc.) and one or more output devices 115 (e.g., a display device). A user interacts with the architecture 100 via the input and output devices 114, 115.

The computer 102 also includes a local storage device 106 and a graphics module 113 (e.g., graphics card) for storing information and generating graphical objects, respectively. The local storage device 106 can be a computer-readable medium. The term “computer-readable medium” refers to any medium that participates in providing instructions to a processor for execution, including without limitation, non-volatile media (e.g., optical or magnetic disks), volatile media (e.g., memory) and transmission media. Transmission media includes, without limitation, coaxial cables, copper wire, fiber optics, and computer buses. Transmission media can also take the form of acoustic, light or radio frequency waves.

While dashboards and widgets are described herein with respect to a personal computer 102, it should be apparent that the disclosed implementations can be incorporated in, or integrated with, any electronic device that is capable of using widgets, including without limitation, portable and desktop computers, servers, electronics, media players, game devices, mobile phones, email devices, personal digital assistants (PDAs), embedded devices, televisions, etc.

A system and methods are provided for managing widgets. The systems and methods can be stand alone, or otherwise integrated into a more comprehensive application. In the materials presented below, an integrated system and method for previewing, installing, managing and operating widgets and dashboards is disclosed. However, one of ordinary skill in the art will recognize that the engines, methods, processes and the like that are described with respect to the management of widgets can themselves be an individual process or application, part of an operating system, a plug-in or the like. In one implementation, the system and methods can be implemented as one or more plug-ins that are installed and run on the personal computer 102. The plug-ins are configured to interact with an operating system (e.g., MAC OS® X, WINDOWS XP, LINUX, etc.) and to perform the various dashboard, management and widget functions, as described with respect of FIGS. 2-7. A system and method for previewing, installing, managing and operating widgets and dashboards can also be implemented as one or more software applications running on the computer 102. Such a system and method can be another widget that is configurable to communicate with other widgets, applications and/or operating systems. Such a system and method can also be characterized as a framework or model that can be implemented on various platforms and/or networks (e.g., client/server networks, stand-alone computers, portable electronic devices, mobile phones, etc.), and/or embedded or bundled with one or more software applications (e.g., email, media player, browser, etc.).

For illustrative purposes, in the following description the invention is described as a feature of an operating system 305 (FIG. 3) for use in installing and managing widgets in a dashboard environment; however, one skilled in the art will recognize that the techniques of the present invention can be implemented in other contexts as well, including those described above, to install and manage other elements, and in other environments including environments associated with applications or operating systems (e.g., a desktop environment, a display environment associated with a browser executing on a mobile communication device, etc.). Examples of other environments include e-mail environments, desktop environments, application environments, hand-held display environments, and other display environments.

Dashboard Overview

FIG. 2 is a flow diagram of an implementation of a process for activating and using a dashboard. A dashboard layer (also referred to herein as a “unified interest layer” or “dashboard”) is used to manage and display widgets. A user can invoke a dashboard (202) by hitting a designated function key or key combination, or by clicking on an icon, or by selecting a command from an onscreen menu, or by moving an onscreen cursor to a designated corner of the screen. In response to such user input, the current state of the user interface is saved (203), the user interface is temporarily inactivated (204), an animation or effect is played or presented to introduce the dashboard (205) and the dashboard is displayed with one or more widgets (206). If applicable, a previous state of the dashboard is retrieved, so that the dashboard can be displayed in its previous configuration.

In some implementations, the dashboard is overlaid on an existing desktop user interface (UI). When the dashboard is activated, the existing UI may be faded, darkened, brightened, blurred, distorted, or otherwise altered to emphasize that it is temporarily inactivated. The existing desktop may or may not be visible behind the dashboard. The desktop can also be shrunk to a small portion of the display screen while the dashboard is active, and can be re-activated by clicking on it. In some implementations, the desktop is shrunk and presented as a widget. The desktop can be re-activated by clicking on the widget.

The user interacts with and/or configures widgets as desired including managing the display of the widgets in the display environment (207). In some implementations, the user can move widgets around the screen, and can resize widgets if applicable. A user can enable certain widgets from a list of available widgets, retrieve, preview, install, import, export, email, or otherwise manage the widgets. Widget management is discussed in greater detail below.

The user dismisses the dashboard (208) by invoking a dismissal command, which causes the normal UI to return or re-present itself to the display screen. In some implementations, the dashboard is dismissed when the user presses a function key or key combination (which may be the same or different than the key or combination used to activate the dashboard), or clicks on a close box or other icon, or clicks on negative space within the dashboard (e.g., a space between widgets), or moves an onscreen cursor to a predefined corner of the screen.

In some implementations, the dashboard is automatically dismissed (i.e., without user input) after some predetermined period of time or in response to a trigger event. An animation or other effect is played or presented to provide a transition as the dashboard is dismissed (209). When the dashboard is dismissed, the current configuration or state of the widgets (e.g., position, size, etc.) can be stored, so that it can be retrieved the next time the dashboard is activated. In some implementations, an animation or effect is played or presented when re-introducing the UI. The UI is restored to its previous state (210) so that the user can resume interaction with software applications and/or the computer operating system.

In some implementations, the dashboard is configurable. The user can select a number of widgets to be displayed, for example, by dragging the widgets from a configuration bar (or other user interface element) onto the dashboard, or by selecting widgets to be enabled from a list of available widgets using a management presentation window. Management presentation windows are discussed in greater detail below. The configuration bar can include different types of widgets, and can be categorized and/or hierarchically organized. In some implementations, in response to the user dragging a widget onto the configuration bar, the widget is downloaded from a server and automatically installed (if not previously installed). In some implementations, certain widgets must be purchased, so the user is requested to provide a credit card number or some other form of payment before the widget is installed on the user's machine. In some implementations, widgets are already installed on the user's machine, but are only made visible when they have been dragged from the configuration bar onto the dashboard or enabled (e.g., by checking an enable box associated with a given widget in a UI presented by a widget manager). The configuration bar is merely an example of one type of UI element for configuring the dashboard. Other configuration mechanisms can be used, such as a widget manager, an icon tray, or menu system.

It should be apparent that there are many ways in which dashboards and widgets can be displayed other than those implementations described herein. For example, widgets can be displayed on any user interface or user interface element, including but not limited to desktops, browser or application windows, menu systems, trays, multi-touch sensitive displays and other widgets.

Software Architecture

FIG. 3 is a block diagram of a software architecture 300 for implementing one or more dashboards, and displaying and managing widgets. The software architecture 300 generally includes a dashboard server 301, one or more dashboard clients 302, an operating system 305 and one or more widgets 303. The server 301 and/or clients 302 use dashboard configuration information 304 to specify configuration options for displaying the widgets 303, including access levels and the like (if applicable). Such configuration information can include information for two or more dashboards configured by the same user or by different users.

In some implementations, the widgets 303 are displayed using HTML and related web technology. The dashboard server 301 can manage and launch the dashboard client 302 processes. In one implementation, each dashboard client 302 loads a widget 303 (e.g., an HTML webpage) and related resources needed to display the page. In some implementations, the dashboard clients 302 display the widgets 303 without a conventional window frame, menu bar, or other components typically associated with on-screen windows. This technique provides a clean, straightforward display of the overall dashboard to reduce confusion and clutter. One or more dashboard clients 302 can display their respective widgets 303 by rendering web pages into a “WebView,” as described in U.S. patent application Ser. No. 11/148,010, entitled “Preview and Installation of User Interface Elements in a Display Environment.” The size of each WebView is defined as metadata associated with the corresponding widget 303. The server 301 provides data for rendering a separate layer that can be overlaid on the normal desktop of the user interface. The widgets 303 are rendered into the separate layer which, in one implementation, is drawn on top of the normal desktop, so as to partially or completely obscure the desktop while the dashboard is active.

Dashboard Server

The dashboard server 301 can be a stand-alone process, embedded in another process, or part of the operating system 305. The server 301 can be located at the computer 102 or at the remote server 107. In some implementations, the server 301 provides functionality for one or more processes, including but not limited to: non-widget UI management, window management, fast login, event management, loading widgets, widget arbitration, Core Image integration and widget preference management, as described in U.S. patent application Ser. No. 11/148,010, entitled “Preview and Installation of User Interface Elements in a Display Environment.”

Dashboard Client

In some implementations, a dashboard client 302 is a process that uses, for example, objects that are defined as part of a development environment, such as Apple Computer's Cocoa Application Framework (also referred to as the Application Kit, or AppKit) for the Mac OS® operating system. In some implementations, the dashboard clients 302 can be implemented as simplified browser screens that omit conventional interface features such as a menu bar, window frame, and the like.

Widget Format

In one implementation, each widget 303 is implemented as an HTML file. The HTML file can reference other local and remote resources such as style sheets (e.g., Cascading Style Sheets), other HTML files, JavaScript files, images, and the like. Widgets 303 can be implemented using, for example, a flat bundle file format or a packaged HTML file format. In some implementations, the Flat Bundle format includes an info.plist file.

The Info.plist files describe a widget 303 and provide an identifier for a widget 303. Table I provides an example of Info.plist file contents.

TABLE I Example of Info.plist File Contents Key Type Description/Value CFBundleIdentifier CFString com.apple.widget <widget name> CFBundleName CFString Name of the widget. MainHTML CFString Name of main HTML resource. Width CFNumber Default width of the widget. Height CFNumber Default height of the widget. DefaultImage CFString Resource name of default PNG file. Plugin (optional) CFString Resource name of native plug-in. AllowFileAccessOutsideofWidget Boolean Access to files across the file system; limited by the users permissions. AllowFullAccess Boolean Access to the file system, Web Kit and standard browser plug-ins, Java applets, network resources, and command-line utilities. AllowInternetPlugins Boolean Access to Web Kit and standard browser plug-ins. AllowJava Boolean Access to Java applets. AllowNetworkAccess Boolean Access to any resources that are not file based. AllowSystem Boolean Access to command- line utilities using widget script object.

The keys AllowFileAccessOutsideofWidget, AllowFullAccess AllowInternetPlugins, AllowJava, AllowNetworkAccess, and AllowSystem are Boolean types that can be set by a widget author to enable certain levels of resource access.

Dashboard Invocation

FIG. 4 a depicts a desktop user interface 400 prior to activation of a dashboard. The desktop user interface 400 (also referred to herein as “desktop”) is a conventional user interface as may be provided by an operating system, such as Mac OS®. The desktop 400 has a background image, menu bar 401, and other standard features. As is known in the art, the desktop 400 may also include windows, icons, and other elements (not shown). The user activates the dashboard by selecting an item from a menu, or by clicking on an icon, or by pressing a function key or key combination, or by some other means for invoking activation.

FIG. 4 b depicts an initial state for a dashboard layer 402. In some implementations, a configuration bar icon 403 is initially displayed. Alternatively, upon activation the dashboard layer 402 can display one or more default widgets 405, 407. If the dashboard layer 402 has previously been activated and configured, the widgets 405, 407, can be displayed as previously configured. As shown in FIG. 4 b, the dashboard layer 402 is not necessarily visible as a distinct layer. However, its various components (such as widgets, icons, and other features) are visible. In some implementations, these components are displayed in a transparent layer, thus maintaining the visibility of the desktop 400 to the user. In some implementations, the desktop 400 and its components are darkened (or blurred, or otherwise visually modified) while the dashboard layer 402 is active, so as to emphasize that the desktop 400 is temporarily inactive. In other implementations, the desktop 400 is not visible while the dashboard layer 402 is active. The user can reactivate the desktop 400 and dismiss the dashboard layer 402 by clicking on an area of the screen where no dashboard element is displayed (i.e., “negative space”). In some implementations, other commands, key combinations, icons, or other user input can be used to dismiss the dashboard layer 402.

In some implementations, the user can drag the icon 403 to any location on the screen, and the position of the icon 403 will remain persistent from one invocation of the dashboard layer 402 to the next. The user can click on the icon 403 to activate the configuration bar 408, as shown in FIG. 4 c. The configuration bar 408 provides access to various widgets that can be placed on the dashboard. In some implementations, a text label is shown for each available widget (e.g., calculator, stocks, iTunes®, etc.). In some implementations, an icon is shown for each available widget (e.g., calculator icon 410). If many widgets are available, the widgets may be arranged hierarchically by type (e.g., game widgets, utility widgets, etc.), or alphabetically, or by any other categorization methodology. For example, a number of categories may be displayed, and clicking on one of the categories causes a pull-down menu to be displayed, listing a number of widgets in that category. In some implementations, a buy widget 406 is also available, allowing the user to select widgets from an online store or website.

Note that the particular configuration and appearance of configuration bar 408 in FIG. 4 c is merely exemplary, and that many other arrangements are possible. For example, widgets can be installed from other locations, other applications or other environments, without requiring that they first be part of the configuration bar 408. The user can dismiss the configuration bar 408 by clicking on dismissal button or icon 404.

Alternative Implementation of Configuration Bar

FIGS. 4 g-4 i illustrate an alternative implementation for deleting a widget from a configuration bar 416. For example, when a user moves a cursor onto the “calculator” label (e.g., a mouse-over) associated with a calculator widget 418, the label is highlighted or otherwise altered, and a delete mechanism (e.g., a delete button) is displayed. If the user clicks or otherwise invokes the delete mechanism, a confirmation overlay 420 is displayed asking the user to confirm the removal and/or deletion of the “calculator” widget. In some implementations, the confirmation overlay 420 is semi-translucent. If the user requests deletion (e.g., clicking the “yes” button), then the calculator widget 418 is removed from the configuration bar 416, as shown in FIG. 4 i.

Installation of Elements

Elements, including user interface elements such as widgets can be installed in a display environment as discussed below. One display environment, a dashboard, will be used for illustrative purposes. Installation can include a preview operation. Installation can include selection of the element, such as by a drag and drop action. Other selection means can be used. In one example, a user can drag widgets from configuration bar 408 onto the surface of the dashboard (in other words, anywhere on the screen), using standard drag-and-drop functionality for moving objects on a screen. Alternatively, the user can select widgets by selecting particular ones of the widgets to be enabled in management presentation window as is discussed in greater detail below.

FIG. 4 d depicts the selection of a calculator widget icon 410 from the configuration bar 408. A calculator icon 410 associated with a calculator widget 409 is highlighted, or otherwise augmented or embellished, to indicate that it has been selected by a user with cursor 411.

In some implementations, widgets in the configuration bar 408 are smaller than their actual size when installed. When the user clicks on a widget and begins to drag it into a dashboard or other display environment, the widget is animated to its actual or installed size to assist the user in the real-time layout of the dashboard. By animating the widget to its actual size, the user will know the actual size of the widget prior to its installation.

In some implementations, an animation, such as a ripple animation, is shown when the user “drops” a widget by releasing a mouse button (or equivalent input device) to place a widget at the desired location. In one implementation, the dragging of the widget to the dashboard invokes an installation process for installing the widget including previewing. After installation, the user can move a widget, to any other desired location, or can remove the widget from the screen, for example by dragging it off the screen, or dragging it back onto the configuration bar 408, by invoking a remove command, disabling a widget in a menu associated with a widget manager or canceling the installation during the preview. In some implementations, the position, state, and configuration of a widget are preserved when the dashboard layer 402 is dismissed, so that these characteristics are restored the next time the dashboard layer 402 is activated.

In some implementations, widgets and/or dashboards (including widgets) can be installed from within a running application. For example, a widget and/or dashboard (including widgets) can be an attachment to an email. When the user clicks the attachment, an installation process is invoked for the widget and/or dashboard which can also include a preview.

Widgets can be created or instantiated using an installer process. The installer process can include a separate user interface or an integrated user interface (e.g., integrated in the display environment or separate from the display environment, for example, in another display environment associated with another application, such as an email application) for selecting and installing widgets in a display environment. For example, a widget received as an email attachment can be launched by a user from directly within a user interface of the email application.

Widgets can be installed, managed and/or instantiated using an installer process. The installer process can include a separate user interface or an integrated user interface (e.g., integrated in the display environment or separate from the display environment for example in another display environment associated with another application, such as an email application) for selecting, installing and managing widgets in a display environment. Thus, the installation area for the widget can be embedded within an application display area or window. For example, if a user receives a widget as an attachment to an email, the user can invoke and install the widget from within the email message window without the need for a separate installation window.

Installation processes for widgets are described in U.S. Provisional Patent Application Ser. No. 60/734,016, entitled “Preview including Theme Based Installation of User Interface Elements in a Display Environment,” including additional functionality related to preview, security, themes and deletion functionality. The installer process can include management functionality. Alternatively, a separate management process can be provided. As used herein, the term “process” refers to a combination of functions that can be implemented in hardware, software, firmware or the like. By way of example, an installer based implementation is discussed below. Other variations are possible.

Installer Process Engines Including Management Engine

By way of example, management functions for managing various aspects of the display of widgets in a display environment can be incorporated in an installer process. FIG. 5 is a block diagram of an installer process 500 for installing widgets in a display environment, including a selection engine 543, a security engine 544, a preview engine 545, a theme engine 546, an installation engine 547 including a management engine 548, and a deletion engine 549.

Selection Engine

The selection engine 543 is used to select and present (e.g., a static presentation) a widget for installation. The selection engine 543 can be invoked in a display environment and can produce an installation area (e.g., a dialog, a panel, a window, etc., and hereinafter referred to as an “installation window”), that acknowledges the user's initiation of the installer process. The installation window can include a presentation of a selected widget (or a reference thereto as described below), along with various buttons that may be activated by the user or otherwise to invoke functionality in the installer process.

A screen shot showing an installation window 450 in a user interface is shown in FIG. 4 e. Installation window 450 can include one or more interactive features (e.g., buttons) that allow a user to install (e.g., install button 452), or cancel the operation (e.g., cancel button 454). In some implementations, preview is automatic. Alternatively, preview can be selected for enablement prior to installation. Installation window 450 can include a reference 456 and a prompt 458, as described below.

In some implementations, the installation window 450 is invoked by clicking on a widget file or package. For example, a weather widget file 413 (e.g., “weather.wdgt”) can be downloaded to the desktop 400 from a web site. When the user double clicks the “weather.wdgt” file with cursor 411, the installation window 450 is displayed in the dashboard layer 402, as shown in FIG. 4 e.

Security Engine

The security engine 544 is used to determine a security access level (or risk level, or both) for either the user or the element to be installed. Security engine 544 can be used to limit the ability of the user to install particular kinds of elements (e.g., based on categories or criteria). In addition or alternatively, security engine 544 is used to determine a security access level (or risk level or both) of an element to be installed. Based on the security access/risk level, one or more operational or functional constraints can be placed on the element during the preview process. For example, limitations on the ability of the previewed element to interact, access, read or write data, monitor output of other system resources, access other system resources, or other limitations can be invoked. The invocation can be temporary, for a predetermined time period, or until the preview has terminated and completed (non-limited) installation has been performed. Functionality or operations of the element can be enabled or disabled, depending on the access level. The security engine 544 can use metadata associated with the element to be installed, user input, contextual information, file type information, default data, read/write preferences, cookies and/or other information to determine the access/risk level. Access control lists including white lists (e.g., including lists identifying certified or otherwise safe elements), black lists (e.g., including lists identifying un-certified or otherwise un-safe elements) and the like can be used to determine the access/risk level.

Various techniques for widget security are described in U.S. Provisional Patent Application No. 60/730,956, entitled “Widget Security,”.

Preview Engine

The preview engine 545 is used to preview (e.g., dynamically) an element (e.g., a widget) that has been selected to be installed. Referring again to FIG. 4 f, the preview engine 545, when invoked, provides an area (hereinafter “a presentation area or presentation window 462” or specifically a “widget window” when used to display a widget) into which the selected element can be displayed. Preview is discussed in greater detail in U.S. patent application Ser. No. 11/148,010, for “Preview and Installation of User Interface Elements in a Display Environment.”

Associated with the preview is a preview designator 464. In one implementation, the preview designator 464 is displayed along with the user interface element being installed (e.g., widget). The preview designator 464 can be of the form of a frame, a carpet on which the presentation window 462 is disposed, a preview theme element, or other designator that overlays, surrounds, bounds or otherwise is associated with the presentation window 462. The combination of the presentation window 462 and the preview designator 464 comprise an installation area for the user interface element to be installed. The installation area can be part of the display environment in to which the element is to be installed (e.g., part of the dashboard) or part of a separate display environment (e.g., part of another user interface, another user interface element, another application, or process, etc.).

When displaying a fully interactive widget in the presentation window 462, user input can be accepted that can result in changes in the presentation. For example, if the widget includes a URL that may be linked to, interaction can include the generation of an underlying page request and the presentation of the requested page in the presentation window 462. Interaction with user interface elements is described in U.S. patent application Ser. No. 11/145,561, for “Application Clipper.” If the interaction is not allowed, a display prompt can be shown to indicate that the operation or function is temporarily disabled during the preview operation.

Window Manager

In some implementations, a window manager 550 is associated with the preview engine 545. The window manager 550 can be a separate process that is used to support the interaction between the presentation window 462, preview designator 464 and the installation window 460 described above. Window management is described in greater detail in U.S. Provisional Patent Application Ser. No. 60/734,016, for “Preview including Theme Based Installation of User Interface Elements in a Display Environment.”

Theme Engine

Theme engine 546 is operative to provide additional content to accompany the content displayed in the presentation window or installation window. The theme engine 546 is operative to determine a theme to be associated with an item to be installed (e.g., a widget), identify additional content for concurrent display, and facilitate the display of the additional content. Additional content can be of the form of a frame that is used to bound the item to be installed on one or more sides. Examples of additional content include a picture frame, a content player (e.g., a video player, a still image player, etc.). The additional content can be static or include functional elements (e.g., buttons, for example to play content). Themes and processes associated therewith are discussed in greater detail in “Preview including Theme Based Installation of User Interface Elements in a Display Environment.”

Installation Engine

The installation engine 547 is operative to install/instantiate the selected widget in the display environment. The installation engine 547 can copy or move as required the selected widget to an appropriate volume and store the data structures (including preference data, identification data, scripts, navigation data and the like) for use in the display environment. In some implementations, the installation engine 547 includes an automatic invocation of the underlying display environment with the installed user interface element presented (i.e., the installation engine 547 installs the widget in, and opens up, a dashboard including the installed widget in a preview mode). Associated with the installation engine 547 can be a management engine 548 for managing all aspects of control and presentation of widgets. Management engines are discussed in greater detail below.

Deletion Engine

The deletion engine 549 provides control for widgets after installation. The deletion engine 549 can be a separate process from the installer process 541, or included therein. The deletion engine 549 can receive input and display user interface elements (dialogs and the like) to ensure that deletion operations are effectuated as required. The deletion engine 549 can be responsive to the selection of a user interface element, a portion of the element, controls associated with the element and the like.

In some implementations, the installer process 541 is part of a separate process that is not associated with a dashboard. Alternatively, the installer process 541 can be part of a dashboard application and be activated, by for example, by selecting a widget for addition to the dashboard, or by selecting a management or installation icon or the like. Selection can include for example double clicking on a widget displayed in a configuration bar 408, selecting a widget for import from another system or environment and the like (shown in FIG. 4 c). Other installation tools are possible.

Dashboard Environment

In a dashboard environment, one or both of the installer process 541 or management process including management functions discussed below can include either or both of a widget bar and a management palette and an associated installer process. The installer process when invoked can cause the display of the widget bar or the management palette in the user interface. In one implementation, the dashboard itself, as currently configured can also be displayed when the installer process is invoked. The installer process can then be invoked to select available widgets for installation/enablement, preview widgets, or remove installed widgets (e.g., remove widgets from the widget bar) depending on the configuration of the installer process.

Desktop Environment

In a desktop environment, installer process 541 or management process can be of the form of an application that can be invoked (automatically, by the user, by the operating system, by an application or other invocation tool) to present user interface elements that are available to be installed/enabled in the desktop environment. The installer application can include one or both of a user interface element bar and a management palette and an associated installer process. The installer process when invoked can cause the display of the user interface element bar and/or management palette in the user interface. The installer process can then be invoked to select available user interface elements for installation/enablement, preview user interface elements, or remove installed user interface elements (i.e., remove user interface elements from the user interface elements bar) depending on the configuration of the installer process.

Installation Process

FIG. 6 is a flow diagram of a process for installing a user interface element (e.g., a widget) in a display environment. The process includes identifying a user interface element (602). Identifying the user interface element can include locating a widget. Locating can include using a search tool or the like to locate widgets available for installation. Alternatively, other methods can be used for identifying user interface elements for installation including automatic and user controlled identification methods. Available widgets can be presented in a list, e.g., by a management process as is shown below.

After identification, the identified user interface element is selected for installation (604). Selecting a user interface element can include selecting a user interface element from a configuration bar (e.g., configuration bar 408), a widget bar, a tool bar, a menu, an authoring application, or other source. Alternatively, selecting can include dragging or dropping the user interface element onto a display environment (e.g., a dashboard layer), downloading the user interface element from a content source or other source, or other selection process. Selecting can include launching an associated installation process for installing the user interface element, a preview application for previewing the user interface element prior to installation or other application including authoring applications. The launching of the applications can be automatic or user or otherwise selectively controlled.

Upon receipt of the selection, an installation window is presented (e.g., installation window 460). In some implementations, the installation window includes a user interface display portion, a prompt, and one or more interactivity elements. The user interface display portion can include a reference, partial display, or complete (e.g., complete but for the ability to interact, a static display) display of the user interface element that has been selected. The reference (e.g., reference 456) can be a complete reference, a pointer, a designator, a still image, or otherwise that identifies the candidate user interface element for installation. In this way, the user is able to recognize that the selection made corresponds to content (e.g., a widget) that the user desires to install.

The prompt can be of the form of a confirmation to the user of the underlying action (e.g., prompt 458). In one implementation the prompt can be used to confirm a desire to install a named widget. In other implementations, the prompt can be used to confirm not only the named user interface element for installation, but the display environment into which the user interface element will be installed (e.g., “Install named widget #1 on my desktop?” or “Install widget #1 on dashboard #1 of 2?”). In still other implementations, the prompt can include a confirmation of an action (e.g., “install the widget and open it in my dashboard”).

The interactivity elements can be of the form of buttons or the like. In one implementation, the installation window includes two interactivity elements including a cancel element (e.g., a cancel button 454), and an installation element (e.g., an installation button 452). Other interactivity elements are possible, including those that link to other associated applications, content sources (e.g., to allow for the selection of a different widget for installation), preview option (e.g., if not automatically previewed) and the like.

Continuing with the method, if a preview option is selected or required (optional), then a preview of the widget in a preview environment is created and presented (606). The creation of the preview environment can include the invocation of a window management engine (e.g., window manager 550) for managing the interaction of one or more windows that make up the preview. In some implementations, the preview includes a presentation window (e.g., presentation window 462) and a preview designator (e.g., preview designator 464) that are separate processes. The presentation window is used to display an instantiation of the selected widget. In some implementations, the display of the presentation window includes an instantiation of the selected widget in a selectable interactive environment. The preview designator is provided to clearly indicate that the preview operation is being performed, as opposed to a conventional direct installation. In some implementations, the preview is presented at a same location in the user interface. Alternatively, if other elements are present at this location, another location or a temporary overlay can be used. In some implementations, the preview designator is a carpet, onto which the presentation window is laid (e.g., layered, overlaid, or the like).

In some implementations, theme content can be presented along with the user interface element in the preview installation window. The theme content can include a theme presentation element that operates as the preview designator (e.g., additional content that is recognized as being part of a preview of an item, for example a preview Title or the like). Other theme content can be presented to preview how the final installed version of the user interface element will appear. For example, assuming a theme border is to be presented with the user interface element at installation, the preview can include the same theme border.

Associated with the preview process may be an authoring or selection process. For example, if the preview displayed is not satisfactory to a user (e.g., the theme content is unsatisfactory), an interactivity element can be presented in the user interface to allow the direct launching of another process (e.g., a search process or application, an authoring application, a selection application or other process or application so that a more appropriate/desirable user interface element can be located/installed) with or without terminating the installation process.

Finally, the user interface element can be installed (608). The installation of the user interface element can include the installation on a tool bar (e.g., a widget bar), in a resource, in a widget manager (e.g., in a list managed by a widget management process) or in a display environment (e.g., directly on a dashboard or the desktop). Installation can include the saving of the underlying content metadata including data structures defining the user interface element in a library or the like. Alternatively, the installation can be part of an underlying application (e.g., directly in an associated dashboard application or a library associated therewith). In some implementations, the installation of the user interface element includes the removal of the preview designator. For example, where a carpet is used to designate the preview, the carpet can be removed for the final installation. In one implementation, the final installation is performed at a same location in the user interface as the preview. In some implementations, an animation or other transition effect can be used when moving from preview to final installed user interface elements. Transitions can include the appearance of pulling of a carpet preview designator from under the user interface element or otherwise making the carpet disappear.

The process steps described can be performed in other orders, repeated or the like to provide desired results. For example, the preview process can be repeated in association with the selection of multiple different user interface elements prior to invoking the installation step.

Once installed, user interface elements can be removed/deleted, enabled and disabled from the display environment as required. In some implementations, a separate deletion process and/or management process is provided from the installation process. Alternatively, the installer process can be invoked to remove/delete and enable/disable user interface elements as required.

In some implementations, deletion includes deactivating the widget but the widget remains installed on the system or device. Alternatively, deletion includes removing the widget completely from the system or device. If a request to delete a widget is received in response to a user action (or programmatically by the operating system or another application), then a message providing the user with deletion options can be presented, enabling the user to determine whether the widget will be deactivated and/or removed from the system or device. In some implementations, the system or device executes a default deletion option which can be changed by the user via a preference pane or other input mechanism, or overwritten by an application or other software component or device (e.g., security engine 544).

Widget Searching

In some implementations, widgets are associated with a widget data type or other metadata to enable a search engine (e.g., Apple's Spotlight® search engine) to search for widgets in files, documents, images, emails, applications, etc. Widgets can be indexed based on data type and/or other metadata. For example, a query can be generated requesting a list of all widgets on a host machine and/other machines on a network. The search engine accesses the index to locate widgets on the host machine and/or other machines on a network.

Widget Manager

As the number of widgets presented in a display environment increases, the need for a tool to organize, and manage widgets (both new and old) arises. In some implementations, a widget manager can be provided to manage installation, access control, security, content control, historical archive, revision, classification, deletion, organization, enablement, placement, importation, exportation, and other functions associated with widgets. With the addition of multiple display environments (e.g., multiple dashboards), the widget manager can provide these and other functions across the multiple display environments to ensure easy of use, flexibility, and customization of each display environment. Below, a number of examples of widget manager instantiations are described. Those of ordinary skill in the art will recognize that the instantiations are exemplary of tools that can be used to enhance the user interface experience and that other variations are possible.

In some implementations, the widget manager is a stand alone application that can be invoked by the user to manage, as described above, widgets. Alternatively, the widget manager can be part of an installer engine as described above, part of an operating system (such as MAC OS X), or a plug in. The widget manager can be a separate process or part of another process executing on an electronic device. The widget manager can be invoked directly, automatically or otherwise as required to allow for interaction with a user. Examples are set forth below with regard to a widget manager and widget manager functions. Those of ordinary skill in the art will recognize that other configurations, including custom configurations based on the device or application, and the like are possible.

In some implementations, a widget manager includes a management engine (similar to management engine 548 discussed above) that is operable to present available widgets in a palette of a user interface display environment, selectively enable or disable each of the available widgets and display enabled widgets in the display environment. In some implementations, the management engine is further operable to locate widgets for installation in the display environment. Location can include locating widgets associated with a given user, display environment or context. Location can include locating widgets for importation from other applications (e.g., e-mail attachments and the like), or from other sources (e.g., web sources). In some implementations, the management engine is further operable to install widgets into the display environment. Accordingly, while reference has been made above concerning one possible implementation where management functions are included in an installer process, other implementations are possible including one where installation functions are included as part of a management process. The display environment can be a user interface of an electronic device.

In some implementations, a widget manager allows users to inspect, remove, enable and disable widgets. The widget manager can be a preference pane or palette, a standalone application or a plug-in, or be part of the installer process described above. The widget manager displays widget information, including but not limited to the widget's title, author, version, class, type, ratings, description, etc. The information can be displayed in any order and format according to one or more sorting criteria, such as alphabetical or chronological order, author, class, rating, etc. In some implementations, the widget manager tracks widget updates and automatically notifies the user or host system or device when an update is available.

In some implementations, the widget manager allows users to perform certain actions on widgets, including but not limited to copying, moving, deleting, uninstalling, deactivating, enabling, disabling, renaming, previewing, etc. In some implementations, the widget manager includes functionality that allows the import and export of widgets to and from various widget sources (e.g., network, email, CD ROM, etc.). For example, widgets can be imported and exported to and from a web site that can be accessed by multiple users. In some implementations, the widget manager includes a search field that allows users to search for widgets on a host system or device, and/or one or more networked devices.

In some implementations, the widget manager can be invoked by a button or other input mechanism located in a user interface (e.g., desktop, system tray, dashboard, configuration bar, etc.). For example, when the button is activated, the widget manager is launched and a user interface is displayed. In_some implementations, the widget manager is a widget itself and includes at least some characteristics, attributes or properties of other widgets. For example, the widget manager can be enabled or disabled, resized, dragged and dropped, flipped to reveal special options or preferences, etc.

In some implementations, the widget manager can be displayed in a format that is consistent with a dashboard theme or content. The appearance_and/or properties of the widget (e.g., colors, styles, fonts, etc.) can be changed by a user via a preference pane or other input mechanism.

Example User Interface for a Widget Manager

FIG. 7 a illustrates a user interface 702 for a widget manager. It should be apparent that a user interface for a widget manager can include more or fewer features than shown.

In some implementations, the user interface 702 is displayed in another user interface 700 (e.g., a desktop or dashboard) in response to user input. User input can include, for example, clicking on a button 716 (e.g., a “Manage Widgets” button) or other input mechanism located in the user interface 700. The user interface 702 can be dismissed by clicking on button 722 or other input mechanism.

In some implementations, the user interface 702 includes a scrollable list 706 of widget names and/or other attributes which correspond to widgets that have been installed on the host system. Double clicking on the name of a widget (or an associated icon or button) launches the widget. In some implementations, the scrollable list 706 includes widgets that reside on the host system but have not been installed (e.g., widgets downloaded to a desktop). This implementation enables users to install or launch widgets from within the widget manager. In some implementations, the list 706 includes names of widgets that reside on another device coupled to the host system via a network connection. In some implementations, a search history is maintained to enable the user to refine search terms and/or re-run a previous search. In some implementations, an event history is maintained which allows users to undo and redo previous widget operations.

Optionally, next to each widget is an icon image 710 associated with the widget that can be used to identify the widget and assist the user in selecting the widget from the list 706. Widgets that are selected to be hidden (e.g., based on a “hide widget” option provided in the widget manager) will not be shown in the list.

The widgets can be scrolled using, for example, a scroll bar 712. Users can also toggle each widget on and off (i.e., enable/disable the widget) by selecting a checkbox 708 located to the left of each widget listing. Similarly, on the right side of some widget listings is a button 707 or other input mechanism that allows users to delete the widget. Note that for this example, widgets that cannot be deleted do not have a corresponding button 707. In some implementation, default widgets or widgets that have been locked may not be deleted.

In some implementations, the user interface 702 includes a menu 704 (e.g., located at the top of the user interface 702) of sorting options that will sort the widget list 706 by name, date, author, rating or any other sorting criteria. In some implementations, the menu 704 includes an option to sort widgets based on whether the widgets are enabled or disabled.

In some implementations, a button 714 (e.g., a button labeled “More Widgets . . . ”) displays more widgets and a search button 713 allows a user to search for more widgets located in local directories or on one or more network devices (e.g., a website) using known search technologies. For example, the user can enter the query “Sports Widgets” in a search box and click the button 713 to initiate a search for Sports Widgets.

In some implementations, when a widget is enabled (check box 708 is checked) the widget's icon image 720 is displayed in a configuration bar 718 in user interface 700. For example, since the check box 708 associated with the “weather widget” is checked, its icon image 720 is displayed in the configuration bar 718 in user interface 700. Similarly, if the check box 708 is unchecked, then the image icon 720 is not displayed or otherwise deemphasized in the configuration bar 718 or its appearance is altered (e.g., grayed out, darkened, made translucent, etc.) to indicate to a user that the widget is disabled.

FIG. 7 b illustrates a widget manager overlay 730 for requesting a user to confirm the deletion of a widget. In some implementations, when clicking the delete button 707 (FIG. 7 a), a semi-translucent overlay 730 appears within the user interface 702 including a message 728 requesting the user to confirm their intent to delete the widget. For example, the message 728 could be “Move this widget to the Trash?” The user can respond to the message 728 by clicking a button 726 (“OK”), which results in the widget being moved to the “Trash” or otherwise deleted from the host system. The user can also respond by clicking a button 724 (“Cancel”), which results in the deletion operation being terminated. If a widget is moved to the “Trash” or otherwise deleted, then its icon image 720 is removed from the configuration bar 718 and list.

Simple Widget Management

Referring now to FIG. 7 c, in one implementation, the widget manager 740 is a process that includes a sorting engine 742, enablement engine 744, a history engine 746 and a presentation engine 748. The widget manager 740 can be a separate computer process, part of an application, or part of the operating system in a computing environment. Though reference has been made that separate engines are provided, the functions of one or more engines can be combined into a single engine or process. For the purposes of clarity of the disclosure, separate engines are described. Other instantiations are possible.

Sorting engine 742 maintains a list 743 of available widgets, in for example a database (not shown). Sorting engine 742 can be used to sort the entries in the list 743, and present the entries in particular orders based on one or more user sort criteria. In one implementation, the list 743 can include information for each widget. The information can be directly or indirectly associated with the widget. For example, information relating to the name, origin, date, version, type (e.g., type of widget selected from clipviews, webviews, accessories, etc,) and other directly related information can be stored in the list 743 or associated with a given widget. Sorting engine 742 can be used to sort the entries in the list 743 to provide a sorted list for presentation by the presentation engine 748 to a user. Other information including historical access data, preferences, and the like can be stored and used as sort criteria. For example, sorting engine 742 can include a separate or integrated process for gathering statistics regarding the use of widgets (most popular, most often accessed, most often accessed in a given context, most recently accessed, and the like). The statistical metadata can be stored in the list 743. Sorting can be invoked by a keystroke, command, automatically based on preferences, or otherwise with user interaction. Sorting is discussed in greater detail below.

Enablement engine 744 is a portion of the manager process that controls which widgets will be provided in a given display environment. Enablement engine 744 receives input from the user either directly or via preferences, to selectively enable ones of the available widgets in a given display environment. Where there is but a single display environment, enablement engine 744 is used to enable selected ones of the available widgets in the display environment. In a multiple display environment setting, enablement engine 744 can be used to selectively enable ones of the available widgets in each of the display environments. Associated with each available widget can be enablement metadata. The enablement metadata can be stored in list 743. The enablement metadata can define the conditions (e.g., display environment, or other conditions) which must be satisfied in order to allow the widget to be displayed in a given display environment. Enablement engine 744 can at the time of launch, or installation of a display environment (e.g., a dashboard), evaluate the enablement data, and enable selected widgets in the display environment.

History engine 746 can be used to maintain historical information relating to widgets in, for example, list 743. Historical information can include use data, snapshot data (reflecting a state of the widget at a given time), version information, statistical information and the like. History engine 746 can be used to review the historical information, reconstruct a historical event (e.g., reconfigure a widget to a default state) or otherwise.

Presentation engine 748 provides a user interface for the widget manager 740. The presentation engine 748 can provide a complete presentation, or one modified based on the display environment. Details of the operation of the presentation manager 748 are discussed below.

In one implementation, the widget manager 740 can be accessed by a keystroke or other command from, for example, the user interface. In one implementation, as shown in FIG. 7 d, the widget manager can be invoked using a button 750 that is located on the user interface, in the example shown, above a configuration bar. In one implementation, the widget manager 740 is itself a widget that is presented in the configuration bar, in a display environment or otherwise that can be activated by user input. For example as shown in FIG. 7 e, the widget manager 740 can be invoked by selecting (e.g., clicking) the widget icon 752 in the configuration bar (e.g., previously referred to as the Widget Bar).

After invocation, a widget management window 760 is presented in the user interface (e.g., by the presentation engine 748) as shown in FIG. 7 f. In some implementations, a full management window is presented. In display environments that are limited by resources, in hardware, software, size or otherwise, a reduced widget management window may be presented. The reduced widget management window can be smaller in size, display less information, or otherwise be optimized to the limited resource environment in which it is displayed. In the implementation shown, widget management window 760 includes a list of widgets 762, and a plurality of input mechanisms (e.g., sort menu 764 and more button 766). Though reference is made to a button, other forms of activating tools are possible including scripts, windows, bars, or other user interface elements. The term button is used generically, and can be accomplished by a variety of means by those of ordinary skill in the art.

Widget list 762 can include a name 770, an icon or image 772, and an enable button 774. In one implementation, the widget list 762 is associated with a list of available widgets (e.g., list 743) that is maintained by the widget manager 740. The list can be maintained in memory associated with the widget manager 740, and called to populate the widget list 762 as required. Alternatively, the widget list 762 can be unique to the user, and represent a subset of the available widgets in the list 743. The determination of which widgets to present can be made based on criteria associated with the user, context or display environment. The name 770 can be the name of the widget, other metadata associated with the widget (e.g., a pointer to a location in memory where the widget is stored, metadata relating to when the widget was installed, where it was installed, what version number, the source of the widget, etc.). Icon 772 can be a representation associated with the widget. The representation can provide a visual clue to the operation of the associated widget (e.g., a calendar widget could have an associated calendar representation). Enable button 774 can be used to selectively enable available widgets in the display environment. Selection of the enable button associated with a given widget marks the widget for enablement at invocation of the display environment. Enable button 774 can be of the form of a check box as described above. Marked widgets can be invoked in the display environment by, for example enablement engine 744. Unmarked widgets can be hidden, not displayed, not installed or otherwise disabled in the display environment at invocation. In one implementation, the widget list 762 can be sorted to show those items that are enabled versus those disabled. Enablement can be controlled by the user, by an administrator, using content guards or filtering technologies as required. For example, widget manager 740 can include a filter that automatically disables ones of the widgets that would otherwise be available based on a criteria (e.g., parent control criteria, access control criteria or otherwise). In one implementation, enablement engine 744 controls access, and hence enablement for individual widgets.

Sort button 764 can be used to sort widget list 762 in the presentation window. Sort button 764 can include a sort criteria selection for defining the sort criteria. The sort criteria can be provided by the user. Alternatively, the sort criteria can be inferred. In one implementation, the sort button 764 can include a plurality of sort options, presented, for example as pull down selections when the sort button is activated as shown in FIG. 7 g. Exemplary sort options include sorting alphabetically, by type, source, preference, use, context, and the like, and sorting automatically based on user provided criteria.

More button 766 can be invoked to display lists, locations (e.g., web locations), stores, suppliers, or otherwise associated with widgets. In one implementation, more button 766 can be a link to a hosting site that provides widgets available for download. When invoked, more button 766 displays additional widgets that are available for installation, or can be used as a browser to locate available widgets.

An alternative implementation for a management window is shown in FIG. 7 h. In the implementation shown, one or more entries in the widget list 762 include an additional button or activatable feature. In the implementation shown, a delete button 768 is included in the user interface. The delete button 768 (shown as a minus sign in one implementation) can be used to remove the widget from the management environment and the computing environment as required. In one implementation, selection of the deletion button 768 provides a prompt to the user to confirm that the widget is to be removed from the widget manager as shown in FIG. 7 i. In one implementation, the widget can be removed from the widget manager list of available widgets and software associated with the widget can be made available for removal (e.g., placed in the trash). In other implementations, a deleted widget is only removed from the management window, and not removed from the computing/display device. In one implementation, only authorized users are able to delete widgets (e.g., an administrator or user with administrator privileges).

Widget Management Including Sorting and Enablement

Referring now to FIG. 7 j, a method is described for managing widgets in a display environment. At invocation, prompt, or otherwise, a list of available widgets is presented in the display environment 770. The list of available widgets can be drawn from a file of widgets stored on the device. At the time of presentation, the list is sorted in accordance with a user preference or with default preferences 772. Enabled widgets can be designated in the presentation 774. A user selection for sorting, enabling, disabling, or otherwise manipulating the list can be received 776. Otherwise manipulating can include viewing information associated with one or more of the widgets in the list. Responsive to the user selection, the list can be managed to reflect the user selection including enabling, disabling, deleting or otherwise processing the widgets in the list 778. Other user selections can be processed 777 until a deactivation event is sensed 780. At deactivation, the list can be stored including any changed data for future retrieval.

Widget Management Including Instantiation of Widgets

Referring now to FIG. 7 k, in one implementation, a method of managing widgets for display in a display environment includes presenting a list of available widgets 785 and receiving user input to enable one or more widgets to be displayed in the display environment 787. The method includes indicating in the list which widgets are enabled and to be displayed in the display environment from the available widgets 789. At run time, the method includes instantiating each enabled widget in the display environment 791. Presenting the list of available widgets can include presenting a link to a location where widgets can be downloaded and sorting the list. Presenting can also include indicating in the list which widgets are disabled and will not be displayed at run time.

Widget Management Including Usage Criteria Presentation

Referring now to FIG. 8 a, in another implementation, a method of managing widgets for display in a display environment includes determining usage information for widgets when displayed in a display environment 801 and determining usage criteria associated with the presentation of widgets in the display environment 803. The method includes selectively enabling and disabling at least one widget from the available widgets based on the usage criteria and the usage information 805 and displaying enabled widgets in the display environment 807. Usage information can be related to a single user or to a plurality of users. For example, the usage information can include usage statistics relative to the individual user, or a pre-defined group of users. In one implementation, the usage information includes an indication of when a given widget was last activated. The usage criteria can define how to use the usage information. For example, in one implementation, the usage criteria can include information on how often the usage information is to be evaluated.

Widget Management Including Enabling a Subset of Widgets

Referring now to FIG. 8 b, in another implementation, a method is provided for managing a subset of widgets in a given display environment. The method includes presenting a list of available widgets in a user interface 820, enabling a subset of the available widgets 822 and displaying the subset in a display environment of the user interface 824. The method can include selecting a widget from the list of available widgets and sending the widget to another user. Sending can include sending the widget using a transfer protocol (e.g., mail protocol or a file transfer protocol). The method can include storing a copy of at least one enabled widget to guard against file corruption. The method can further include downloading a widget from an external source and installing the downloaded widget. Installing the downloaded widget can include previewing the downloaded widget in a display environment. Downloading the widget can also include determining user privileges including classification privileges, determining a type of the widget and enabling the download only if the classification privileges allow downloading of widgets of the determined type.

The method can include selectively controlling user configuration of available widgets including controlling one or more of enabling, editing, removing, or disabling widgets. The method can include storing historical configuration data for one or more of each widget or a selected subset of widgets.

Widget Management Including Privilege Processing

Referring now to FIG. 8 c, in one implementation, a method of managing widgets includes privilege processing. Privilege processing as used herein, refers to consideration of the privileges associated with a given user to make presentation decisions relative to the number, or kind of widgets that are available for instantiation in a display environment. The method includes determining user privileges 830, presenting a list of available widgets based on the user privileges 832, enabling a subset of the available widgets based on user privilege 834 and displaying enabled widgets in a display environment 836.

Determining user privileges can include authenticating the user. The method can further include loading of a new widget for display, verifying privileges of the user prior to display of the new widget and selectively enabling or disabling display of the new widget based on the user privileges. Presenting a list of available widgets can include determining a type of each widget and making available only widgets having types that are consistent with the user privileges. The type can be based on content displayed by the widget. Presenting a list of available widgets can include rating each widget and making available only those widgets having ratings that are consistent with the user privileges.

Widget Management Using Classification Data

Referring to FIG. 8 d, in another implementation, particular widgets for display can be determined based on classification. Classification can relate to content associated with or displayed by a given widget. Classification can also relate to type of widget in terms of functionality (e.g., webviews, or widgets able to retrieve pages from the internet). Other classification criteria are possible including classifications based on usage, popularity, preference or otherwise. Classification data can be derived by the system or be provided or otherwise associated with a given widget. A method for managing widgets based on classification can include determining widgets that are available for display 840, classifying the available widgets 842, presenting the available widgets according to the classification 844, selectively enabling ones of the available widgets 846, and, at run time, displaying enabled widgets in a display environment 848.

Classifying the available widgets can include sorting the available widgets in accordance with criteria. The criteria can be based on usage of the available widgets or type of widget. Methods associated with criteria selection are discussed below.

In another implementation, a method for managing widgets includes identifying available widgets for display in a display environment, determining criteria for selecting ones of the available widgets and displaying the selected ones of the available widgets. The criteria can be a random selection or based on usage data associated with the available widgets or be defined by the user.

Widget Management in a Dedicated Management Environment Including Geometry Presentation

As discussed above, the management of widgets can be accomplished as a separate process, or within the confines of another process, such as an installer process. In a management environment, administrative and user roles can be provided. Further, in a management environment, customized management tools can be provided to assist either the administrator or the user in the deployment and maintenance of widgets in a given display environment. One example of a custom tool is a geometry tool. A geometry tool can be used to organize the presentation of widgets in the display environment. The geometry tool can have associated display geometry that defines how widgets are to be displayed. The display geometry can include patterns or the like for defining the presentation of enabled widgets in the display environment. Examples include a clock pattern, a square pattern, a three dimensional cube or other patterns. As such, a separate process that focuses just on the management functionalities can be beneficial. In the implementation shown in FIG. 8 e, a method of managing widgets includes identifying available widgets for display in a display environment 850, presenting the available widgets in a management environment 852, selectively enabling ones of the available widgets 854, and displaying enabled widgets in the display environment 856.

Displaying enabled widgets can include controlling placement of each widget in the display environment in accordance with a display geometry. The display geometry can define a location for each widget in the display environment. The method can include identifying a new widget for installation, installing the new widget including previewing the new widget in a location in the display environment defined by the display geometry, and selectively installing the new widget after the preview including adding the new widget in the presentation of the available widgets.

In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the invention.

In particular, one skilled in the art will recognize that other architectures and graphics environments may be used, and that the present invention can be implemented using graphics tools and products other than those described above. In particular, the client/server approach is merely one example of an architecture for providing the dashboard functionality of the present invention; one skilled in the art will recognize that other, non-client/server approaches can also be used.

Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

The algorithms and modules presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatuses to perform the method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, features, attributes, methodologies, and other aspects of the invention can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component of the present invention is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present invention is in no way limited to implementation in any specific operating system or environment.

It will be understood by those skilled in the relevant art that the above-described implementations are merely exemplary, and many changes can be made without departing from the true spirit and scope of the present invention. Therefore, it is intended by the appended claims to cover all such changes and modifications that come within the true spirit and scope of this invention. 

1. A widget manager comprising: a management engine operable to present available widgets in a palette of a user interface display environment; selectively enable or disable each of the available widgets; and display enabled widgets in the display environment, where an enabled widget presently executes an associated function including providing a presentation aspect associated with the executing function, and where selectively enabling or disabling includes selecting a widget for enabling or disabling based on statistics for usage of a given widget by one or more users and criteria for evaluating the statistics, wherein the statistics for usage including statistics for how often over a time period the given widget was enabled by the one or more users and when the respective widget was last enabled and wherein the usage criteria include information on how often the usage information is to be evaluated.
 2. The widget manager of claim 1, wherein the management engine is further operable to locate widgets for installation in the display environment.
 3. The widget manager of claim 1, wherein the management engine is further operable to install widgets into the display environment.
 4. The widget manager of claim 3, wherein installing widgets includes previewing widgets in the display environment.
 5. The widget manager of claim 1, wherein the display environment is a user interface of an electronic device.
 6. A method of managing widgets for display in a display environment, comprising: determining usage information for widgets when displayed in a display environment, the usage information including statistics for usage by one or more users of each respective widget, the statistics for usage including statistics for how often over a time period the respective widget was enabled by the one or more users and when the respective widget was last enabled; determining usage criteria associated with the presentation of widgets in the display environment, the usage criteria defining how to evaluate the usage information in order to make a selection of one or more of the widgets for presentation in the display environment, the usage criteria include information on how often the usage information is to be evaluated; selectively enabling at least one widget from available widgets based on the usage criteria and the usage information; and displaying enabled widgets in the display environment.
 7. The method of claim 6, wherein determining usage information includes determining usage information for more than one user.
 8. The method of claim 6, wherein activation includes user interaction with the widget.
 9. A method for managing widgets, comprising: identifying available widgets for display in a display environment; determining criteria for selecting ones of the available widgets, the criteria defining which widgets to select based on usage statistics of the widgets by one or more users, the usage statistics related to display of the widgets previously in a display environment and including statistics for how often over a time period a respective widget was displayed by the one or more users; determining how often to evaluate the criteria including determining a time period; after expiration of a time period, displaying and enabling selected ones of the available widgets, where an enabled widget presently executes an associated function including providing a presentation aspect associated with the executing function.
 10. The method of claim 9, wherein the criteria is a random selection.
 11. The method of claim 9, wherein the criteria are based on usage data associated with the available widgets.
 12. The method of claim 9, wherein the criteria are defined by the user.
 13. A computer-readable storage medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: determining usage information for widgets when displayed in a display environment the usage information including statistics for usage by one or more users of each respective widget related to display of the widgets previously in a display environment and including statistics for how often over a time period a respective widget was displayed by the one or more users and when the respective widget was last displayed; determining usage criteria associated with the presentation of widgets in the display environment, the usage criteria defining how to evaluate the usage information in order to make a selection of one or more of the widgets for presentation in the display environment, the usage criteria include information on how often the usage information is to be evaluated; selectively enabling at least one widget from available widgets based on the usage criteria and the usage information; and displaying enabled widgets in the display environment.
 14. A computer-readable storage medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: identifying available widgets for display in a display environment; determining information and criteria for selecting ones of the available widgets, the information defining which widgets to select based on usage statistics associated with the widgets, the usage statistics related to display of the widgets previously in a display environment by one or more users and including statistics for how often over a time period a respective widget was displayed by the one or more users and when the respective widget was last displayed, the criteria defining how to evaluate the information in order to make a selection of one or more of the widgets for presentation in the display environment, the criteria defining how often the information is to be evaluated; displaying and enabling selected ones of the available widgets, where an enabled widget presently executes an associated function including providing a presentation aspect associated with the executing function. 